Tuesday, March 8, 2005

[Technical Assistance and Documentation]

ToolChest

Backup Certification Matrices

Disk Shelf Firmware

SnapDrive™ 3.1.1 for Windows Description Page

Features of this Release

SnapDrive 3.1.1 includes several important bug fixes, as well as support for the following SnapDrive 3.1 features:

Separately licensable modules for Multipath I/O (MPIO) and SnapDrive
Distinguishing between a bootable Logical Unit Number (LUN) and a standard LUN
Fibre Channel Protocol (FCP) and Internet SCSI (iSCSI) support on the same Windows® host (each LUN supports only one protocol)
Integration of NetApp® Volume Shadow Copy Service (VSS) Hardware Provider
Internationalization compliant -verified with Japanese and German versions of Windows

SnapDrive 3.1.1 also recognizes Microsoft Windows Hardware Quality Lab (WHQL) certified iSCSI host bus adapters (HBAs).

NOTE: At this time, Network Appliance has completed verification of the Intel iSCSI HBA from the iSCSI Host Attach Kit for Windows with SnapDrive and the QLogic QLA4010 iSCSI HBA for use with SnapDrive. Network Appliance continues to work with other iSCSI HBA vendors to ensure compatibility with SnapDrive.

Bugs Fixed in this Release

The following bugs have been fixed in SnapDrive 3.1.1. Click on the bug number for more information on a specific bug.

135104 - SnapManager database and transaction log verification operation fail when on Windows Server 2003 Standard Edition when drive letter Z:\ is assigned to the CDROM or other removable storage devices.

139971 - Snapmanager verification with SD3.1 fails if verification server cannot use the same filer IP as the Exchange server used in the backup.

140834 - Unable to create a snapshot of virtual disks when filer has more than one IP address and both reachable from same host.

141316 - Snapshot mount fails if space available on the volume is less than size of the LUN in snapshot on Data ONTAP versions prior to 7.0 due to ONTAP burt 130299.

142896 - On installation of SnapDrive 3.1, user name and password are in cleartext in navp*.log, located in Program Files\SnapDrive installation directory. After upgrade completes, user can delete navp*.log files with date/time prior to upgrade to SnapDrive 3.1D3.

140767 - A Win2k3/W2K host over FCP may lose connection to its LUNs in the following MPIO situations:

Host SCSI I/O times out due to filer taking longer time than Disk TimeoutValue setting allows to complete the I/O (set on host).

Snapdrive 3.1.1 adds additional retry requests to the MPIO module. In addition, the Disk "TimeoutValue" must be set to > 190 (Reg key: HKLM\System\CurrentControlSet\Services\Disk).

Upgrading from any previous version of SnapDrive will set this value correctly. However, a clean install of SnapDrive 3.1.1
will require this value to be set, which can be done by editing the registry value, or by re-running the 3.1.1 installation.
Under heavy load, and continuous running of takeover/giveback for extended periods of time, a host may lose connection to its LUNs. This release greatly mitigates this problem and makes the MPIO solution more robust.

147714 - System hang is caused by recursively acquiring spinlock in NTAPDSM. Only applies to MPIO based systems and only when first device in the group (LUN) is set to DISABLED while running I/O.

139345 - "FCP PARTNER PATH MISCONFIGURED" being reported for no apparent reason.
A change was made to the MPIO algorithm to be target based instead of HBA based. This change will prevent "FCP PARTNER PATH MISCONFIGURED" error from being misreported.

147572 - Changed SnapDrive to use different API call to do proper LUN enumeration on both Qlogic and Emulex FCP HBAs (146293 is duplicate).

134494 - Root of burt 140995. Both bugs are fixed in this release with the inclusion of updated MPIO driver from Microsoft.
All users running 3.1D2 or 3.1D4 should upgrade to SnapDrive 3.1.1.

Limitations

SnapDrive 3.1.1 does not support the following:

Management of virtual local disk-types (VLDs)
Use of MPIO on iSCSI
Use of 64-bit Windows
Use of LUN cloning
Use of virtual disks managed by SnapDrive, as in
- Dynamic disk
- Raw disk
Use of qtree quotas (However, SnapDrive does support the use of qtrees without quotas.)
Use of SnapMirror® functionality to replicate individual qtrees (However, SnapDrive does support the use of SnapMirror to replicate volumes.)
Connection to Data ONTAP MultiStore™ virtual filer partitions (However, SnapDrive can connect directly to the physical "hosting" filer [vfiler0] in a MultiStore installation.)
A virtual disk as an extended partition. SnapDrive only supports a single, primary partition on a virtual disk.

NOTE: SnapDrive 3.1.1 supports the use of the Microsoft iSCSI software initiator version 1.06. See the SnapManager and SnapDrive Compatibility Matrix for the most current information.

System Requirements

The following table lists the SnapDrive system requirements.

Component	Requirement
Operating system on the filer	Data ONTAP 6.4.4 or 6.5.1 software
Operating system on the filer	Note: For the most current list of supported Data ONTAP software versions, see the SnapManager and SnapDrive Compatibility Matrix.
Licenses enabled on the filer	iSCSI, if you plan to use iSCSI-accessed virtual disks FCP, if you plan to use FCP-accessed virtual disks SnapRestore™ software, which is required only for restoring virtual disks from snapshots SnapMirror, if you plan to use the SnapMirror option
Licenses enabled on the filer	Note: The iSCSI and FCP licenses supplied with SnapDrive enable all the CIFS functionality necessary for using SnapDrive. If you also want full-featured, direct CIFS access to a particular filer, you must install a separate CIFS license on that filer.
Hardware on the Windows host machine	500 MHZ Pentium® III 256 MB system RAM Emulex® LP9002L-F2 HBAs for FCP, supplied by NetApp.
	Note: To determine the number and type of HBAs and NICs required by each host in your SnapDrive configuration, see the section on selecting a SnapDrive configuration in the SnapDrive 3.1 Installation and Administration Guide. The guide is available on the NetApp on the Web (NOW) site at http://now.netapp.com/. From the NOW site, navigate to the documentation section.

	Note: Obtain the latest firmware and drivers for the HBAs and network interface cards (NICs) you are using, to ensure high network bandwidth and ease of configuration. The NIC you use to facilitate data transfer for the Microsoft iSCSI software initiator can come from any vendor, but must have the appropriate LOGO certification: "Designed for Windows Server 2003" or "Designed for Windows 2000". The latest FCP driver and firmware is available on the NOW site at http:// now.netapp.com/NOW/cgi-bin/software/. From this gateway, navigate to the SAN (FCP) Host Attach Kit for Windows download page. The Microsoft iSCSI software initiator must be downloaded from the Microsoft site. For directions and links, go to the NOW site at http://now.netapp.com/NOW/cgi-bin/software/, scroll to the iSCSI Host Support Kit item, select the appropriate platform, and then click Go.
Operating system on the Windows host machine	One of the following operating systems: Windows 2000 Server with Service Pack 4 (SP4) Windows 2000 Advanced Server with SP4 (for Windows-cluster configurations) Windows 2003 Server Standard or Enterprise Editions
Microsoft Windows hotfixes	Before you can install SnapDrive, your host machine must have the appropriate Microsoft post-SP4 hotfixes installed. If your host is running Windows 2000, you must install hotfix 293778. Before installing hotfix 293778, see Bug ID 113541 in "Known issues" of the release notes. If you host is running Windows 2000 and you encounter the problem described in the Microsoft Knowledge Base article 822831, you must install hotfix 822831. In addition, NetApp strongly recommends installing the following hotfixes on your Windows 2000 hosts: Q293778–Ftdisk.sys 5.0.2195.6920 or later. ”Multiple-Path Software May Cause Disk Signature to Change” Q325040–Classpnp.sys 5.0.2195.5912 or later. ”After You Restart Your Computer, an Error Message Occurs, or a Drive Letter Changes, or a Dynamic Disk Is Displayed As BASIC” Q815198–Wmiprov.dll 1.50.1085.99 or later. “WMI Classes Information for Multipath Drivers Is Not Displayed in WBEMTest” Q815616–Classpnp.sys 5.0.2195.5912 or later. “Clustered Disk Drive Letter Unexpectedly Changes” Q838637–Scsiport.sys 5.0.2195.6906 or later. “Computer stops responding when a SCSI miniport driver issues a ScsiPortNotification(BusChangeDetected) call” Q885294–Ntfs.sys 5.0.2195.6973 or later. “Your computer restarts, and you receive a 0xA Stop error in the Ntfs.sys file when you remount a volume” If your host is running Windows 2003, you must install hotfixes 824354, 831112, 833167, 838894, and 840281. Before installing hotfix 840281, see Bug ID 131344 in "Known issues" of the release notes. In addition, NetApp strongly recommends installing the following hotfixes on your Windows 2003 hosts: Q815198–Wmiprov.dll 1.50.1085.99 or later. “WMI Classes Information for Multipath Drivers Is Not Displayed in WBEMTest” Q824354–Clusdisk.sys 5.2.3790.82 or later. “Server stops responding or you receive a stop error message when you set up a Windows Server 2003-based server cluster.” Q833167–Clusdisk.sys 5.2.3790.114 or later, Ftdisk.sys 5.2.3790.113 or later, Vssapi.dll 5.2.3790.113 or later, Vssvc.exe 5.2.3790.113 or later, Vss_ps.dll 5.2.3790.113 or later. “A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003” Q838637-2K3–Scsiport.sys 5.2.3790.142 or later. “Computer stops responding when a SCSI miniport driver issues a ScsiPortNotification(BusChangeDetected) call” Q840281–Clusres.dll 5.2.3790.163 or later. “Volume information is lost when you extend a partition by using the DiskPart tool and then move the volume in a Windows Server 2003 cluster” Q886800–Partmgr.sys 5.2.3790.220 or later. “A disk signature is unexpectedly changed on a Windows Server 2003 clustered physical disk resource” Q887532–Vdsbas.dll 5.2.3790.224 or later. “You may receive the "VDS_E_OBJECT_DELETED" error message when you try to import a transportable shadow volume in Windows Server 2003” Q891793–Storport.sys 5.2.3790.274 or later. “The updated Storport storage driver, version 5.2.3790.274, fixes a range of Storport-related problems in Windows Server 2003”. This hotfix replaces hotfix 883646.
	Note: The Microsoft hotfixes, except for those indicated in the following note, must be requested directly from Microsoft Product Support Services at http://support.microsoft.com/.
	Note: Specify the directory to which you want to download Microsoft post-SP4 hotfix 824354 and/or Microsoft post-SP4 hotfix 822831.

Preinstallation Steps
	Before you download and install SnapDrive, complete the following steps:
	NOTE: Because SnapDrive 3.1 and later has a new license scheme, you must install at least one of either the SnapDrive license for LUN Provisioning and snapshot management or the MPIO license for MPIO path management. These licenses are provided in Step 3 and Step 4.
	Download the iSCSI-protocol license, if you are currently using VLD-type virtual disks. Download the FCP-protocol license, if you are currently using LUN-type virtual disks. Download the SnapDrive license for LUN Provisioning and snapshot management. After you click on the SnapDrive license link, navigate to the license by choosing the "Show me all" search method, selecting SDR-WIN, then clicking Go. Download the MPIO license for MPIO path management. After you click on the MPIO license link, navigate to the license by choosing the "Show me all" search method, selecting SDR-MPIO, then clicking Go. Download the SnapDrive 3.1 Installation and Administration Guide. Read Chapter 3, "Installing or Upgrading SnapDrive," in the SnapDrive 3.1 Installation and Administration Guide.

Product Documentation

Software documentation

To view the Release Notes for this release of SnapDrive, click here.
To view the documentation for this release of SnapDrive, click here.
To download the documentation, select ZIP file format or TAR file format.

NOTE: If you are using the Internet Explorer 4.0 or 5.0 browser and are having problems opening any of the Acrobat® files, you might need to upgrade your browser by downloading the latest Internet Explorer Service Pack. You can also right-click the link and select "Save Target as..." to download the Acrobat file, or you can use the Netscape Navigator™ browser to view or print the document.

Software Download Instructions
	After you confirm that your system meets the SnapDrive requirements and complete the preinstallation steps, proceed with the download by clicking CONTINUE.

Part Number: 215-01319-A0